An event is a special message that is generated on the card asynchronously. This means that it is not the response to a request to the card, but a spontaneous message.
What is the Goal of an Event?
The goal of events is to inform the environment about a changing condition on the card. A message may be broadcast to mark the change in status. The message is volatile and cannot be retrieved from the system after it has been broadcast. There are several means by which the message can be filtered.
Events
The events reported by the 2GF100
| Menu Item | Description |
|
Announcements |
Announcements is not an event. This item is only used for switching the announcement of status changes on/off. 0=off, other =on |
|
Input_A |
Input_A can be selected between 0 .. 255. 0= no event, 1..255 is the priority setting. |
|
Input_B |
Input_B can be selected between 0 .. 255. 0= no event, 1..255 is the priority setting. |
|
Ref-Status |
Reference can be selected between 0 .. 255. 0= no event, 1..255 is the priority setting. |
|
Active_Out_A |
Active output A can be selected between 0 .. 255. 0= no event, 1..255 is the priority setting. |
| Active_Out_B | Active output B can be selected between 0 .. 255. 0= no event, 1..255 is the priority setting. |
What Information is Available in an Event?
The message consists of the following items:
| • | A message string to show what has happened in text, for example: “INP_LOSS”, “REF_LOSS”, “INP_RETURN”. |
| • | A tag that also shows what happens, but with a predefined number: e.g. 1 (= loss of input), 2 (= loss of reference), 129(= 1+128 = return of input). For a list of these predefined tags, please see the table below. |
| • | A priority that marks the importance of an event. This value is defined by the user and can have any value between 1 and 255, or 0 when disabled. |
| • | A slot number of the source of this event. |
Message String
The message string is defined in the card and is therefore fixed. It may be used in controlling software like Synapse Set-up to show the event.
Tags
The tag is also defined in the card. The tag has a fixed meaning. When controlling or monitoring software should make decisions based on events, it is easier to use the tag instead of interpreting a string. The first implementation is the tag-controlled switch in the GPI16.
In cases where the event marks a change to fault status (e.g. 1 for Loss of Input), the complement is marked by the tag increased by 128 (80hex) (e.g. 129 (81hex) for Return of Input).
Defining Tags
The tags defined for the 2GF100
| Event Menu Item | Tag | Description | |
| Announcements | 0 |
8 |
Announcement of report and control values |
| Input_A | 01hex=INP_A_LOSS | 81hex=INP_A_RETURN | Input A lost or returned |
| Input_B | 41hex=INP_B_LOSS | c1hex= INP_B_RETURN | Input B lost or returned |
|
Ref-Status |
02hex=REF_LOSS | 82hex=REF_RETURN | Reference lost or returned |
| Active_Out_A | 19hex=IN_B->OUT_A | 99hex= IN_A->OUT_A | Input B or input A on outputs A |
| Active_Out_B | 1ahex= IN_A->OUT_B | 9ahex=IN_B->OUT_B | Input A or input B on outputs B |
Priority
The priority is a user-defined value. The higher the priority of the alarm, the higher this value will be. Setting the priority to Zero disables the announcement of this alarm. Alarms with priorities equal to or higher than the Error Threshold setting of the RRC will cause the error LED on the Synapse rack front panel to light up.
Card Address
Together with the message string or the tag, the slot number or address of the card is relevant to be able to assign the event to a certain card.